Post sale referral tracking

ABSTRACT

An e-commerce system is provided that tracks purchase transaction across multiple client devices. The e-commerce system stores hop information describing when a customer is exposed to a product of a vendor through an affiliate who advertises the vendor&#39;s products. The e-commerce system determines from the stored hop information which affiliate or affiliates to compensate for the sale of a product. This allows the e-commerce system to determine, after the sale, whether additional affiliates need to be compensated for the sale of the product based on the hop information.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of co-pending U.S. application Ser.No. 13/298,134, filed Nov. 16, 2011, which is incorporated by referencein its entirety.

BACKGROUND

The embodiments disclosed herein relate generally to electronic commerce(e-commerce), and more particularly to tracking e-commerce transactionsacross multiple client devices that are used to conduct the transactionsand provide post sale affiliate referral tracking, affiliate fraud,affiliate attribution, client treatment, or customer quality metricsthat are associated with the transactions, affiliates, or customers.

Conventional e-commerce systems facilitate purchase transactions betweencustomers at client devices and vendors that are associated with thee-commerce systems. Conventional e-commerce systems also allowaffiliates to advertise vendor products on their websites. Theseaffiliates receive commission from vendors for products purchased by wayof the affiliate's website.

Typically, e-commerce systems track affiliate referral to vendorproducts using cookies (i.e., a HTTP cookie) stored on client devices.The e-commerce systems store a cookie on a client device responsive to acustomer using the client device to select a uniform resource locator(URL) link associated with a product that is advertised on anaffiliate's web page. The URL link redirects the client device to avendor's product page which allows the user to purchase the product. Thelimited size of cookies used by conventional e-commerce systemsrestricts the amount of information that can be stored in the cookies.Generally, these cookies comprise information about the vendorassociated with the product and the affiliate that referred the user tothe vendor's product.

When a customer purchases the product, conventional e-commerce systemscan determine the affiliate that contributed to the sale of the productby accessing a cookie stored on the client device thereby allowing theaffiliate to be compensated accordingly. This technique used by thee-commerce systems for affiliate compensation suffers from severaldeficiencies. For example, if a customer has disabled the use of cookieson his or her client device, the e-commerce systems cannot determinewhether the sale of a product should be attributed to an affiliatebecause the systems lack the necessary cookie to determine an affiliatethat referred the product to the customer that made the purchasetransaction.

Furthermore, even if cookies are enabled, a customer may use multipleclient devices to purchase a vendor product which can lead to incorrectattribution of the product sale. For example, a customer may use a firstclient device to visit a product page of a vendor through advertising onan affiliate's website. Accordingly, a cookie is stored on the firstclient device indicating the vendor associated with the product and theaffiliate that referred the product to the customer. However, thecustomer may not complete the purchase of the product using the firstclient device. Rather, at a later time the customer may use a secondclient device to directly access the product page and complete thepurchase of the product. Thus, although an affiliate contributed to thepurchase transaction, the affiliate is not credited for the transactionbecause the second client device lacks affiliate information in a cookiestored at the second client device.

SUMMARY

Embodiments described herein provide techniques for implementation in ane-commerce system by an online marketplace server to detect the use ofmultiple client devices by a single customer when making purchasetransactions with vendors. In one embodiment, the marketplace servercomprises an account database that stores customer activity informationfor customers that complete purchase transactions with vendors that arefacilitated by the marketplace server. The customer activity informationfor a customer may include data records indicative of affiliates thatreferred the customer to vendor products, client devices associated withthe customer, and purchase transaction (orders) information associatedwith the customer.

When a customer's client device is referred to a vendor's website viaadvertising on an affiliate's website, the customer activity informationfor the customer is updated. By storing the customer activityinformation at the marketplace server rather than on a cookie at thecustomer's client device, the marketplace server can accurately monitoror track the affiliates involved in transactions with vendors even ifthose transactions occurred using multiple client devices that areassociated with the customer. This allows for affiliates to be properlycompensated for their referrals to vendor products. Furthermore, becausethe customer activity information is stored at the marketplace serverrather than at the customer's client device, the marketplace server needonly store a cookie at the client device of the customer comprising aunique device identifier of the device. The unique device identifier maybe used to access the customer activity information in the accountdatabase.

Additionally, the marketplace server allows affiliates to be properlycompensated for their product referrals even if cookies are not storedon client devices of customers. If a client device that completed apurchase transaction through the marketplace server lacks a cookie, themarketplace server is not initially aware of the identity of the clientdevice and may not be able to attribute the transaction to an affiliate.However, the marketplace server may utilize the customer activityinformation post sale (i.e., after the transaction) to determine thecustomer or client device associated with the completed purchasetransaction. Because the marketplace server stores transactioninformation, the marketplace server may identify which client device isassociated with the completed transaction and review the customeractivity information to identify instances when one or more affiliatesreferred the purchased product to the customer when using the clientdevice. The marketplace server may also analyze data records of thecustomer's other client devices to determine whether there is anindication that another affiliate(s) referred the purchased product tothe customer when the customer was using his or her other clientdevices. Once the affiliate(s) that contributed to the transaction areidentified from the customer activity information, credit for thetransaction is attributed to the affiliate(s) post sale.

The features and advantages described in the specification are not allinclusive and, in particular, many additional features and advantageswill be apparent to one of ordinary skill in the art in view of thedrawings, specification, and claims. Moreover, it should be noted thatthe language used in the specification has been principally selected forreadability and instructional purposes, and may not have been selectedto delineate or circumscribe the inventive subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a computing environment of an e-commerce system inaccordance with one embodiment.

FIG. 2 illustrates a data record tree of customer activity in accordancewith one embodiment.

FIG. 3 illustrates a method flow diagram for updating customer activityinformation with affiliate referrals in accordance with one embodiment.

FIG. 4A and FIG. 4B illustrate a method flow diagram for determiningpost sale affiliate credit in accordance with one embodiment.

The figures depict various embodiments of the present invention forpurposes of illustration only. One skilled in the art will readilyrecognize from the following discussion that alternative embodiments ofthe structures and methods illustrated herein may be employed withoutdeparting from the principles of the invention described herein.

DETAILED DESCRIPTION

FIG. 1 illustrates an exemplary e-commerce environment 100. One or morecustomers at client devices 105A through 105N are in communication witha marketplace server 103, one or more vendors 107A through 107N, and oneor more affiliates 115A through 115N via a network 101. Embodiments ofthe computer environment 100 may have thousands or millions of clientdevices 105, vendors 107, and affiliates 115 connected to themarketplace server 103 via the network 101.

The client device 105, for example, may be a personal computercomprising a web browser, which allows the customer to communicate withthe marketplace server 103 and vendors 107. In other embodiments, theclient 105 is a network-capable device other than a computer, such as apersonal digital assistant (PDA), a mobile telephone, a tablet computer,a television “set-top box,” etc. The network 101 enables communicationsbetween the marketplace server 103, vendors 107 and client devices 105.In one embodiment, the network 101 uses standard communicationstechnologies and/or protocols. Depending upon the embodiment, thenetwork 101 may include links to or comprise other networks, such as theInternet.

In one embodiment, vendors 107 are entities that sell products tocustomers. The products may include digital products such as electronicbooks (e-books), downloadable software, and/or online services.Alternatively, the products may include any type of product or servicefor which a transaction may be made online, including financial productsand services or subscriptions or shippable products. Vendors 107 work inconjunction with the marketplace server 103 and with affiliates to sellproducts to customers. Each product sold by a vendor 107 has anassociated pitch (product) page that describes the product and adownload URL if the product is a digital product. In one embodiment,each pitch page is associated with a pitch page URL that links to thepitch page. Typically, the pitch page URL is displayed on themarketplace server, in an affiliate's website, and/or a vendor's websitefor advertisement purposes.

In one embodiment, an affiliate of the marketplace server 103 mayadvertise a vendor's products on his or her website. An affiliate 115 isa person or entity that receives commission from vendors 107 or themarketplace server 103 for completed transactions that occur as a resultof the affiliate referring the product to customers on the affiliate'swebsite. In one embodiment, a referrer link is displayed on anaffiliate's website. A referrer link is a web address that directscustomers who click on the link to a vendor's website according to oneembodiment.

Each product is also associated with a download URL. As describedpreviously, products provided by vendors 107 are typically digitalproducts. After a customer purchases a product, the marketplace server103 provides a link to the vendor's web site which includes a downloadURL so that the customer may download the purchased product.

Generally, the marketplace server 103 facilitates purchase transactionsbetween customers at client devices 105 and vendors 107 and directscustomers to pitch pages of products provided by vendors 107. Inalternative embodiments, the marketplace server 103 may also beconsidered a vendor 107 and provide the functionality of a vendor 107 asdescribed herein. That is, the marketplace server 103 may provide itsown products for purchase by customers thereby functioning as a vendor107. A suitable website provided by the marketplace server 103 is foundat www.clickbank.com. Additionally, the marketplace server 103advertises products sold by vendors 107 on the website provided by themarketplace server 103.

As illustrated in FIG. 1, the marketplace server 103 comprises variousmodules including a transaction module 113 and an account database 111.As is known in the art, the term “module” refers to computer programlogic utilized to provide the specified functionality. Thus, a modulecan be implemented in hardware, firmware, and/or software. In oneembodiment, program modules are stored on a non-transitory storagedevice (i.e., a computer program product), loaded into a memory, andexecuted by a computer processor. Additionally, those of skill in theart will recognize that other embodiments of the marketplace server 103shown in FIG. 1 can have different and/or other modules than the onesdescribed here, and that the functionalities can be distributed amongthe modules in a different manner.

In one embodiment, the account database 111 stores customer activityinformation for customers of the marketplace server 103. The accountdatabase 111 may also store account information for affiliates 115 andvendors 107 associated with the account database 111. FIG. 2 illustratesa data record tree 200 for a customer 201 that is representative ofcustomer activity information for the customer 201. The data record tree200 illustrates an association of the customer's various devices, hoprecords, order information, and optionally the client account records ifthe customer is an affiliate or vendor as will be further describedbelow.

As shown in FIG. 2, the data record tree 200 comprises a customer record201. Customers are represented in the marketplace server 103 by theirassociated customer record 201. In one embodiment, each customer record201 comprises a unique customer identifier (ID) that is associated withthe customer. The customer record 201 may also store contact informationfor the customer such as the user's name, electronic mail (e-mail)address(es), residence address, business address, and telephone number.The customer record 201 may also store financial information for thecustomer such as credit card information, bank account information,and/or a payer ID (e.g., a PayPal™ ID).

For each customer record 201, the account database 111 stores a set of ndevices records 203 that are associated with the customer record 201.The set of n device records 203 represents the known client devices thatare used by the customer when interacting with the marketplace server103. In the example illustrated in FIG. 2, customer record 201 isassociated with two device records: device record 203A and device record203B. Each device record 203 comprises a unique device ID that isassociated with a client device 105. The device ID for a given clientdevice 105 may be included in a cookie that is stored on the device. Thedevice ID is used by the marketplace server 103 to identify the datarecord tree 200 associated with the customer that is purchasing aproduct or viewing a pitch page of a product through an affiliate'swebsite.

Furthermore, each device record 203 comprises one or more fingerprintsthat represent the client device 105 associated with the device record203. A fingerprint for a client device 105 may be used to identify theclient device 105 if the client device 105 lacks a cookie with a deviceID. In one embodiment, a device record 203 comprises a first levelfingerprint. The first level fingerprint is a hash of information sentto the marketplace server 103 from a web browser (e.g., MOZILLA FIREFOX,GOOGLE CHROME, MICROSOFT INTERNET EXPLORER, etc.) on the client device105. The marketplace server 103 may assemble an attribute string formedby various attributes or configuration settings of the browser asdescribed in U.S. Pat. No. 7,330,871 filed Jun. 5, 2001, which isincorporated by reference in its entirety. For example, the browser maysend user agent information associated with the web browser comprising astring that identifies the user agent (e.g., a version of the browser).The web browser may also send the internet protocol (IP) addressassociated with the client device 105 when communicating with themarketplace server 103. The marketplace server 103 may apply a hashfunction (i.e., a hash digest) such as MD5, SHA1, etc. to theinformation received from the web browser. The values returned from thehash function represent a first level fingerprint for the client device105 and are stored in the device record 203.

Each device record 203 may also comprises a second level fingerprint.The second level fingerprint is based on device information that themarketplace server 103 requests from the client device 105 associatedwith the device record 203. The marketplace server 203 may store ascript which requests device information from the device 203 that isused to create the second level fingerprint. For example, the script mayrequest information describing the device model number, serial numberassociated with the device, an address associated with the customer thatregistered the device, the IP address associated with the device,installed fonts, installed plug-ins (including the versions of theplug-ins), screen resolution, user agent information, operating systeminformation, and http headers, or any other information that can be usedto represent the device. A hash function as described above may beapplied to the information received in response to the request togenerate the second level fingerprint. The resulting values returnedfrom the hash function represent the second level fingerprint from theclient device 105 and are stored in the device record 203.

In one embodiment, the data tree record 200 for a customer comprises aset of n hop records 205 that are associated with each device record203. The set of n hop records 205 for a device record 203 describe theinteraction between the client device 105 represented by the devicerecord 203 and affiliates of the marketplace server 103. As shown inFIG. 2, device record 203A is associated with n hop records 205A anddevice record 203B is associated with n hop records 205B.

In one embodiment, a hop record describes an associated client device'sexposure to an affiliate referral link (i.e., a specific affiliate)otherwise known as a “hop.” For example, when a customer at a clientdevice 105 selects a redirect on an affiliate's website that directs thecustomer to a vendor's website, the customer redirection to the vendor'swebsite is considered a “hop.” That is, a hop record describes anaffiliate that referred the client device 105 to a product of a vendorusing the client device 105 associated with the hop record.

In one embodiment, a hop record 205 comprises one or more of thefollowing hop attributes:

-   -   a unique customer ID associated with the customer;    -   a unique device ID of the client device 105 that was involved in        the hop described by the hop record 205;    -   an affiliate ID of the affiliate 115 that directed the customer        201 to a vendor's pitch page during the hop;    -   a vendor ID of the vendor 107 associated with the pitch page        that was displayed to the customer during the hop;    -   a URL of the pitch page associated with the hop;    -   user agent (e.g., a browser) information on the client device        105 in communication with the marketplace server 103 during the        hop;    -   a tracking indication from the client device 105 indicative of        whether tracking the customer's interaction with the marketplace        server 103 is allowed;    -   a vendor category associated with the vendor 107 that describes        the type of products sold by the vendor such as “Health &        Fitness”; and    -   a product category associated with the pitch page to which the        customer was redirected to during the hop that describes the        type of product advertised in the pitch page such as “e-books.”

As shown in FIG. 2, the data record tree 200 for the customer alsocomprises a set of n order records 207 that is associated with eachdevice record 203. The set of n order records 207 for a device record203 represents the complete list of purchase transactions of thecustomer that were completed using the client device 105 represented bythe device record 203. In one embodiment, an order record describes aparticular purchase transaction with a vendor 107 through themarketplace server 103 using the client device 105 represented by thedevice record 203. In one embodiment, an order record comprises one ormore of the following order attributes:

-   -   an order ID associated with the order record that represents the        particular purchase transaction;    -   a product ID associated with the product that was purchased in        the purchase transaction;    -   a timestamp that describes the time when the purchase        transaction was completed;    -   the name of the customer associated with the purchase        transaction;    -   an address of the customer associated with the purchase        transaction;    -   an e-mail address of the customer associated with the purchase        transaction; and    -   payment information used to pay for the product associated with        the order record 207 such as the credit card number, credit card        expiration date, and name on the credit card.

In one embodiment, if the customer record 201 is representative of avendor 107 or an affiliate 115 that purchases products through themarketplace server 103, a device record 203 is associated with a set ofn client account records 209. A client account record 209 describesvendor or affiliate account information with the marketplace server 103.The account information may comprise an account ID for the vendor 107 oraffiliate 115, completed purchases associated with the account, one ormore user names associated with the client account, authenticationcredentials for the vendor/affiliate to log into the account, and/or thelast login time to the client account. Storing client account records209 for vendors and affiliates allows the marketplace server 103 toidentify suspicious behavior such as fraud or cookie stuffing. Forexample, the client account record 209 may used to determine that anaffiliate 115 is referring itself when making purchases in order toreduce the price of the purchase. By tracking client logins to themarketplace server 103, the marketplace server 103 may also rejectrefunds submitted by vendors/affiliates that purchase and attempt torefund competitor products or may apply different refund rules to therefund requests. Abusers of a refund policy associated with themarketplace server 103 (e.g., purchasing several products with highrefund rates) may be detected at order time and prevent the purchase ofproducts. Similarly, the marketplace server 103 may provide post saleaffiliate referral tracking, affiliate fraud, affiliate attribution,special client treatment, or customer quality metrics that areassociated with transactions, affiliates, or customers.

Referring back to FIG. 1, the marketplace server 103 comprises atransaction module 113. Generally, the transaction module 113facilitates transactions between customers on client devices 105 andvendors 107. More particularly, the transaction module 113 tracks acustomer's purchase transactions across a plurality of client devices105 and updates the customer's activity information in the accountdatabase 111. The transaction module 113 also updates the customer'sactivity information when the customer is exposed to affiliates of themarketplace server 103. The transaction module 113 utilizes the activityinformation of a customer stored in the account database 111 to unifythe information across multiple client devices.

For example, when a cookie is not stored in a client device 105 or thecookie lacks the unique device ID of the client device 105, thetransaction module 113 uses the customer activity information stored inthe account database 111 to determine the customer ID of the customerthereby exposing which affiliate(s) should be compensated for thepurchase order. Thus, the transaction module 113 can identify one ormore affiliates that are associated with a purchase order even whenmultiple client devices 105 are used by the customer to complete thetransaction or if cookies are not enabled (or unavailable) on the clientdevice 105.

Multiple Device Tracking

Referring now to FIG. 3, one embodiment of a method performed by thetransaction module 113 to update a customer's activity information inthe account database 111 is shown when a customer interacts withaffiliates. Note that other embodiments perform the illustrated steps indifferent orders, and/or perform different or additional steps.

In one embodiment, the transaction module 113 receives 301 a request fora pitch page from a customer's client device 105. For example, thetransaction module 113 may receive an indication that the customerselected a link on an affiliate's website that redirected the clientdevice 105 to a vendor's pitch page. The transaction module 113determines 303 whether there is an existing cookie stored at the clientdevice 105. The transaction module 113 may communicate with the clientdevice 105 requesting that the client device 105 provide the uniquedevice ID stored in the cookie if available. If the client device 105lacks a cookie comprising the device ID of the client device 105, thetransaction module 113 generates 305 a unique device ID for the clientdevice 105. The transaction module 113 provides 307 a cookie comprisingthe unique device ID to the client device 105 for storage.

Responsive to providing the cookie 307 to the client device 105 orresponsive to determining 303 that there is an existing cookie at theclient device 105 that comprises the device ID of the device 105, thetransaction module 113 determines 309 whether the device ID (i.e., therecently created device ID or the device ID included in the existingcookie) is included in the account database 111. If the device ID is notin the account database 111, the transaction module 113 creates a datarecord tree for the customer as described with respect to FIG. 2.

Responsive to creating 311 the data record tree or responsive todetermining 309 that the device ID is included in the account database111, the transaction module 113 creates 313 a hop record and associatesthe hop record with the customer's data tree record. The created hoprecord includes the hop attributes of the affiliate 115 that referredthe customer to the requested pitch page. By creating the hop record,the affiliate information associated with the hop record can be accessedby the transaction module 113 to determine the affiliate 115 thatreferred the product even if the product is not purchased until a latertime. Thus, if the customer uses another client device 105 to purchasethe product at a later time without the customer accessing the pitchpage for the product via the affiliate's website, the affiliate'sreferral of the product is still tracked since it is stored in the hoprecord. Thus, by updating the data record tree for a customer when thecustomer interacts with an affiliate 115, the resulting hop recordensures that the affiliate 115 will be properly compensated forreferring the product to the customer.

In one embodiment, the transaction module 113 also creates 317 afingerprint for the client device 105 and stores the fingerprint in thecustomer's data record tree. The fingerprint may be a first levelfingerprint. The fingerprint may be used to identify the client device105 at a later time if the cookie is no longer stored at the clientdevice 105.

The transaction module 113 creates 317 an updated pitch page redirectand communicates the redirect to the web browser on the client device105. The redirect causes the client device 105 to load the vendor'spitch page for the product of interest. In one embodiment, the updatedpitch page redirect comprises the device ID associated with the clientdevice 105. By having the device ID in the redirect, the transactionmodule 113 may identify and update the proper data record tree for thecustomer based on the device ID if the customer purchases the product.

In one embodiment, the transaction module 317 determines 319 whether thevendor is in a premier vendor program of the marketplace server 103. Inone embodiment, the vendor pays the marketplace server 103 to beclassified as a premier vendor. A vendor may also be promoted to thepremier status after selling a threshold number of products via themarketplace server 103. By being in the premier vendor program, themarketplace server 103 returns the premier vendor's pitch pages as thetop search results in response to search queries for products providedby the premier vendor.

If the vendor is in the premier vendor program, the transaction module113 requests 321 client device information from the client device 105that can be used to generate a second level fingerprint. Thus, by beingin the premier vendor program, the transaction module 317 asserts moreeffort in obtaining information about the vendor's customers. Responsiveto receiving the client device information, the transaction module 113generates the second level fingerprint based on the client deviceinformation and updates 323 the customer's data tree record with thesecond level fingerprint. If the vendor is not in the premier program,the transaction module 317 is done updating the data record tree for thecustomer. The method illustrated in FIG. 3 is repeated when a customeris referred to a pitch page by an affiliate 115 to ensure the datarecord tree for the customer is kept up to date.

Post Sale Affiliate Compensation

Referring back to FIG. 1, in one embodiment the transaction module 113also determines post sale affiliate compensation. That is, after apurchase transaction has been completed, the transaction module 113analyzes the customer activity information stored in the accountdatabase 111 to identify an affiliate(s) that referred a vendor'sproduct to a customer that purchased the product. For example, thetransaction module 113 may analyze the customer activity informationstored in the account database 111 to determine that the affiliate 115that was initially credited for the product order was not the mostdeserving affiliate 115. In one embodiment, the most deserving affiliate115 may be considered the affiliate 115 that initially advertised thepurchased product to the customer if multiple affiliates referred thepurchased product to the customer. Alternatively, the most deservingaffiliate is considered the affiliate that referred the product at thetime of purchase if multiple affiliates referred the purchased productto the customer. Furthermore, if no affiliate 115 was initially creditedfor a referral of a product purchased by a customer because of theabsence of a cookie on the client device 105 of the customer, thetransaction module 113 may identify from the customer activityinformation in the account database 111 an affiliate 115 that referredthe purchased product on another client device that is different fromthe client device that completed the order.

Referring now to FIG. 4A, one embodiment of a method performed by thetransaction module 113 to complete a purchase transaction isillustrated. Note that other embodiments perform the illustrated stepsin different orders, and/or perform different or additional steps.

As shown in FIG. 4A, the transaction module 113 receives 401 a requestto purchase a product from a customer's client device 105. In oneembodiment, the request is received by a way of an affiliate's websitethat referred to the product to the customer. The transaction module 113communicates with the client device 105 to determine 403 whether acookie exists at the client device 105. If a cookie exists at the clientdevice 105, the transaction module 113 identifies 405 the associateddevice record for the client device 105 based on the device ID includedin the cookie.

If the transaction module 113 determines 403 that the client device 105lacks a cookie, the transaction module 113 identifies 407 the clientdevice 105 based on fingerprints associated with the client device 105.In one embodiment, the transaction module 113 generates a first levelfingerprint based on client data received from the browser of the clientdevice 105 and compares the first level fingerprint with first levelfingerprints in the account database 111 to identify a matching firstlevel fingerprint. If the transaction module 113 identifies a match, thetransaction module 113 determines the device ID associated with thematching first level fingerprint. In one embodiment, if the transactionmodule 113 cannot identify the device ID based on the first levelfingerprint for the client device 105, the transaction module 113requests client data from the client device 105 to generate a secondlevel fingerprint. Based on the second level fingerprint, thetransaction module 113 identifies a device ID in the account database111 with a matching second level fingerprint.

After the transaction module 113 has identified the device ID for theclient device 105 based on either the fingerprints or the cookie, thetransaction module 113 traverses 409 the data record tree correspondingto the device ID to identify the set of n hop records associated withthe device ID. Because the device ID corresponds to a device record thatis associated with other device records for the customer, thetransaction module 113 can identify the set of n hop records across allof the other device records for the customer.

The transaction module 113 determines 411 from the set of n hop recordsacross the customer's client devices, one or more hop records that areassociated with the product requested by the client device 105. Thetransaction module 113 may identify the hop records associated with theproduct based on the hop attributes for the hop records. Particularly,the transaction module 113 identifies one or more hop records thatcomprise a URL of the pitch page associated with the requested product.The inclusion of the URL of the pitch page of the requested product in ahop record indicates that the customer viewed the pitch page for theproduct through the website of an affiliate 115 indicated in the hoprecord. Thus, the transaction module 113 identifies a referringaffiliate for compensation purposes for the referral.

The transaction module 113 then processes 413 the purchase order for theproduct. That is, the transaction module 113 may receive the paymentinformation of the customer from the client device 105 and completes thepurchase order using the payment information. Alternatively, thetransaction module 113 identifies the payment information for thecustomer based on payment information stored in the account database 111rather than receive the payment information from the customer at thetime of purchase. The transaction module 113 then distributes 415affiliate credit based on the identified hops that are associated withthe product order. The transaction module 113 may distribute credit toone or more affiliates based on the number of affiliates indicated inthe identified hops related to the purchase transaction. In other words,the transaction module 113 determines how credit is attributed toaffiliates when multiple affiliates are involved in the referral of aproduct.

The transaction module 113 determines the amount of credit attributed toan affiliate 115 from among a plurality of affiliates that contributedto a customer's purchase of a product based on various factors.Particularly, the transaction module 113 measures the contribution ofeach affiliate that influenced the purchase transaction. A customer'sproduct interactions that influenced the customer to purchase a productmay be a result of advertisements displayed on an affiliate's website(e.g., pay per click advertisements or advertisement impressions),e-mail campaigns developed by the affiliate, special offers offered theaffiliate, and/or organic search queries through the affiliate's websiteresulting in the identification of the product.

The affiliate with the greatest influence may receive the greatestattribution. In one embodiment, the amount of credit that an affiliatereceives is based on the number of times the affiliate referred apurchased product to a customer and the total number of times that theproduct was referred to the customer. For example, the hop records inthe account database 111 may indicate that a first affiliate and asecond affiliate both influenced a customer to purchase a product. Thetransaction module 113 may identify that the product was referred to thecustomer a total of 5 times with the first affiliate contributing 4 ofthe referrals and the second affiliate contributing only 1 of thereferrals. The transaction module 113 may determine that the firstaffiliate contributed 80% to the customer's decision to purchase theproduct and the second affiliate contributed 20% to the customer'sdecision to purchase the product based on the total number of referralsand the number of times each affiliate referred the product. Thetransaction module 113 accordingly awards the commission to the firstaffiliate and the second affiliate based on the percentage ofcontribution to the sale of the product.

Alternatively, the affiliate 115 that first referred the customer to theproduct may receive the largest compensation compared to thecompensation received by the other affiliates. The affiliate that firstreferred the customer to the product is compensated the most regardlessof the number of times the affiliate referred the product because thataffiliate initiated the customer's interest in the purchased product.Alternatively, the last affiliate that referred the product prior thecustomer purchasing the product may receive the largest compensationcompared to the compensation received by the other affiliates becausethe last affiliate's referral led to the completion of the transaction.

In another embodiment, the affiliate that first referred the customer tothe product and the last affiliate that referred the product prior tothe customer purchasing the product are the only affiliates that receivecompensation. In another embodiment, if more than two affiliatesreferred the product, the other affiliates that referred the product tothe customer between the exposure of the product by a first affiliateand the exposure of the product by a last affiliate prior to thecustomer purchasing the product also receive compensation, albeit asmaller compensation than the first affiliate and the second affiliate.Alternatively, compensation may be equally distributed to the affiliatesthat referred the product to a customer.

In one embodiment, the credit that an affiliate receives as a result ofa sale of a product through the affiliate's website is designated by thevendor 107 of the purchased product. In one embodiment, the totalcommission may be a flat fee or may be a percentage of the purchaseprice of the product. Thus, the total compensation may be distributed tothe affiliates based on various schemes described above. Othercompensation schemes may be used than those described herein.

Referring now to FIG. 4B, one embodiment of a method performed by thetransaction module 113 to identify post sale affiliate credit is shown.Note that other embodiments perform the illustrated steps in differentorders, and/or perform different or additional steps. Note that stepsillustrated in FIG. 4B are a continuation of the method performed inFIG. 4A in one embodiment.

After distributing affiliate credit based on the identified hops, thetransaction module 113 determines 417 whether the payment informationused to complete the purchase transaction is already stored in theaccount database 111. The account database 111 lacking the paymentinformation used by the customer to conduct the transaction isindicative of the customer not being referred by an affiliate whichcauses the transaction module 113 to determine 419 that post saleaffiliate credit is not required.

If the payment information is included in the account database 111, thetransaction module 111 identifies 421 the data record tree associatedwith the payment information. The transaction module 111 determines 423whether the data record tree associated with the payment information isthe same data record tree associated with the client device 105 used tocomplete the product order. If the data record tree associated with thepayment information is the same data record tree associated with theclient device 105, the transaction module 113 determines 419 that postsale affiliate credit is not required because the traversal of the datarecord tree in step 409 would have already revealed the affiliates thatcontributed to the sale of the purchased product.

If the data record tree associated with the payment information is notthe same data record tree associated with the client device 105, thetransaction module 113 associates the data record tree of the clientdevice 105 with the data record tree associated with the paymentinformation. Thus, although the device ID associated with the paymentinformation is different from the device ID of the client device 105used to make the purchase, having the same payment information spanacross multiple data record trees because of the association can be usedin the future as an indication that the trees are associated with thesame customer. By associating the data record trees to one another, thetransaction module 113 may utilize customer activity information fromboth data record trees when receiving request for products from thevarious device IDs in the data record trees.

The transaction module 113 then determines 427 whether the purchaseorder was associated with an affiliate(s). If an affiliate was alreadyassociated with the purchase order, the transaction module 114determines 419 that post sale affiliate credit is not required. If thepurchase order did not have an associated affiliate, the transactionmodule 113 determines whether the newly associated data record trees 429are indicative of one or more affiliates that referred the product thatwas purchased by the customer. In one embodiment, the transaction module113 traverses the hop records in the associated data record trees todetermine affiliates associated with the referral of the purchasedproduct as previously described with respect to FIG. 4A. If thetransaction module 113 determines that the associated data record treesdo not have any additional affiliates other than those alreadydetermined from step 411, the transaction module 411 determines 419 thatpost sale affiliate credit is not required. However, if the transactionmodule 113 determines that the associated data record trees compriseadditional affiliates than those determined from step 411, thetransaction module 431 provides post sale affiliate credit to theadditional affiliates. Thus, the transaction module 113 has identifiedaffiliates that should be credited for referring the purchased productafter the completion of the purchase transaction using the customeractivity information stored in the account database 111.

Customer Quality Score

In one embodiment, the marketplace server 103 assigns a customer qualityscore to a customer that is indicative of a life time value of thecustomer. The marketplace server 103 may access the customer record of acustomer from the account database 111 to identify one or more of thefollowing purchase trends comprising the recency of the customer's lastpurchase (e.g., 2 weeks ago), the frequency in which the customerpurchases products through the marketplace server 103 (e.g., monthlyorders), and/or an average value of the customer's purchases (e.g.,average order of $50). Based on these factors, the marketplace server103 calculates the customer quality score indicating the life time valueof the customer. For example, a high score (e.g., above a threshold) mayindicate that an associated customer is more valuable because thecustomer frequently makes high purchase transactions compared to othercustomers with a lower score.

The marketplace server 103 may communicate the customer quality scoreand a customer's purchasing trends to vendors 107. The vendors 107 maydynamically modify product offerings to the customer based on thecustomer quality score and the purchase trends of the customer. If acustomer's score indicates a high value customer, the vendor may modifyproduct offerings specific to the customer. For example, if the vendor107 determines that the customer is a high value customer and buysmultiple products within a month each with a value of $50, the vendormay provide to the customer multiple product offerings each costing $50rather than a single product at $30. By providing multiple productofferings, the odds of the customer purchasing a product are increased.

SUMMARY

The foregoing description of the embodiments above has been presentedfor the purpose of illustration; it is not intended to be exhaustive orto limit the invention to the precise forms disclosed. Persons skilledin the relevant art can appreciate that many modifications andvariations are possible in light of the above disclosure.

Some portions of this description describe the embodiments in terms ofalgorithms and symbolic representations of operations on information.These algorithmic descriptions and representations are commonly used bythose skilled in the data processing arts to convey the substance oftheir work effectively to others skilled in the art. These operations,while described functionally, computationally, or logically, areunderstood to be implemented by computer programs or equivalentelectrical circuits, microcode, or the like. Furthermore, it has alsoproven convenient at times, to refer to these arrangements of operationsas modules, without loss of generality. The described operations andtheir associated modules may be embodied in software, firmware,hardware, or any combinations thereof.

Any of the steps, operations, or processes described herein may beperformed or implemented with one or more hardware or software modules,alone or in combination with other devices. In one embodiment, asoftware module is implemented with a computer program productcomprising a non-transitory computer-readable storage medium containingcomputer program code, which can be executed by a computer processor forperforming any or all of the steps, operations, or processes described.

The embodiments may also relate to an apparatus for performing theoperations herein. This apparatus may be specially constructed for therequired purposes, and/or it may comprise a general-purpose computingdevice selectively activated or reconfigured by a computer programstored in the computer. Such a computer program may be stored in anon-transitory, tangible computer readable storage medium, or any typeof media suitable for storing electronic instructions, which may becoupled to a computer system bus. Furthermore, any computing systemsreferred to in the specification may include a single processor or maybe architectures employing multiple processor designs for increasedcomputing capability.

The embodiments may also relate to a product that is produced by acomputing process described herein. Such a product may compriseinformation resulting from a computing process, where the information isstored on a non-transitory, tangible computer readable storage mediumand may include any embodiment of a computer program product or otherdata combination described herein.

Finally, the language used in the specification has been principallyselected for readability and instructional purposes, and it may not havebeen selected to delineate or circumscribe the inventive subject matter.It is therefore intended that the scope of the embodiments describedabove be limited not by this detailed description, but rather by anyclaims that issue on an application based hereon. Accordingly, thedisclosure of the embodiments is intended to be illustrative, but notlimiting, of the scope of the invention, which is set forth in thefollowing claims.

What is claimed is:
 1. A computer-implemented method of a marketplaceserver for determining post sale affiliate compensation, the methodcomprising: receiving, by a computer, payment information from a firstclient device of a customer to purchase a product of a vendor;completing, by the computer, the purchase of the product by the firstclient device; accessing, by the computer, a plurality of records thatdescribe customers of the marketplace server to determine whether thepayment information is included in the plurality of records; responsiveto determining that the payment information is included in a first datarecord associated with a second client device different than the firstclient device, determining, by the computer, whether the first datarecord including the payment information is associated with a seconddata record associated with the first client device; responsive todetermining that the first data record includes the payment informationbut is not associated with the second data record corresponding to thefirst client device that completed the purchase of the product,associating, by the computer, the second data record with the first datarecord; determining, by the computer, from the associated data records,an affiliate that referred the product to the customer; and compensatingthe affiliate for referring to the customer, via the second clientdevice, the product purchased by the customer using the first clientdevice.
 2. The computer-implemented method of claim 1, wherein aplurality of records associated with a customer represents a data recordtree of the customer, the data record tree comprising: a customer recordcomprising attributes of the customer; and one or more device recordsthat are associated with the customer record, a device record describingclient devices associated with the customer; wherein each device recordis associated with one or more hop records describing affiliates thatreferred the customer to products of vendors and is associated with oneor more order records describing purchase transactions of the customerwith the marketplace server using a client device associated with thedevice record.
 3. The computer-implemented method of claim 1, furthercomprising: receiving, from the first client device of the customer, arequest to purchase the product of the vendor; identifying data recordsassociated with the first client device of the customer; anddetermining, from the data records associated with the first clientdevice, whether an affiliate referred the product to the customer; anddetermining, from the data records that an affiliate did not refer theproduct to the customer.
 4. The computer-implemented method of claim 1,wherein determining the affiliate that referred the product comprises:determining a first affiliate and a second affiliate that referred theproduct to the customer; and compensating the first affiliate and thesecond affiliate for referring the product to the customer.
 5. Thecomputer-implemented method of claim 4, wherein the compensationdistributed to the second affiliate is less than the compensationdistributed to the first affiliate.
 6. The computer-implemented methodof claim 4, wherein the compensation distributed to the second affiliateis greater than the compensation distributed to the first affiliate. 7.The computer-implemented method of claim 4, wherein the compensationdistributed to the second affiliate is equal to the compensationdistributed to the first affiliate.
 8. A computer program productcomprising a non-transitory computer-readable storage medium storingcomputer-executable code for determining post sale affiliatecompensation, the code executable to perform steps comprising: receivingpayment information from a first client device of a customer to purchasea product of a vendor; completing the purchase of the product by thefirst client device; accessing a plurality of records that describecustomers of the marketplace server to determine whether the paymentinformation is included in the plurality of records; responsive todetermining that the payment information is included in a first datarecord associated with a second client device different than the firstclient device, determining whether the first data record including thepayment information is associated with a second data record associatedwith the first client device; responsive to determining that the firstdata record includes the payment information but is not associated withthe second data record corresponding to the first client device thatcompleted the purchase of the product, associating the second datarecord with the first data record; determining, from the associated datarecords, an affiliate that referred the product to the customer; andcompensating the affiliate for referring to the customer, via the secondclient device, the product purchased by the customer using the firstclient device.
 9. The computer program product of claim 8, wherein aplurality of records associated with a customer represents a data recordtree of the customer, the data record tree comprising: a customer recordcomprising attributes of the customer; and one or more device recordsthat are associated with the customer record, a device record describingclient devices associated with the customer; wherein each device recordis associated with one or more hop records describing affiliates thatreferred the customer to products of vendors and is associated with oneor more order records describing purchase transactions of the customerwith the marketplace server using a client device associated with thedevice record.
 10. The computer program product of claim 8, the codeexecutable to perform further steps comprising: receiving, from thefirst client device of the customer, a request to purchase the productof the vendor; identifying data records associated with the first clientdevice of the customer; and determining, from the data recordsassociated with the first client device, whether an affiliate referredthe product to the customer; and determining, from the data records thatan affiliate did not refer the product to the customer.
 11. The computerprogram product of claim 8, wherein determining the affiliate thatreferred the product comprises: determining a first affiliate and asecond affiliate that referred the product to the customer; andcompensating the first affiliate and the second affiliate for referringthe product to the customer.
 12. The computer program product of claim11, wherein the compensation distributed to the second affiliate is lessthan the compensation distributed to the first affiliate.
 13. Thecomputer program product of claim 11, wherein the compensationdistributed to the second affiliate is greater than the compensationdistributed to the first affiliate.
 14. The computer program product ofclaim 11, wherein the compensation distributed to the second affiliateis equal to the compensation distributed to the first affiliate.
 15. Acomputer system for determining post sale affiliate compensation, thesystem comprising: a computer processor; and a non-transitorycomputer-readable storage medium storing executable instructionsconfigured to execute on the computer processor, the instructions whenexecuted by the computer processor are configured to perform stepscomprising: receiving payment information from a first client device ofa customer to purchase a product of a vendor; completing the purchase ofthe product by the first client device; accessing a plurality of recordsthat describe customers of the marketplace server to determine whetherthe payment information is included in the plurality of records;responsive to determining that the payment information is included in afirst data record associated with a second client device different thanthe first client device, determining whether the first data recordincluding the payment information is associated with a second datarecord associated with the first client device; responsive todetermining that the first data record includes the payment informationbut is not associated with the second data record corresponding to thefirst client device that completed the purchase of the product,associating the second data record with the first data record;determining, from the associated data records, an affiliate thatreferred the product to the customer; and compensating the affiliate forreferring to the customer, via the second client device, the productpurchased by the customer using the first client device.
 16. Thecomputer system of claim 15, wherein a plurality of records associatedwith a customer represent a data record tree of the customer, the datarecord tree comprising: a customer record comprising attributes of thecustomer; and one or more device records that are associated with thecustomer record, a device record describing client devices associatedwith the customer; wherein each device record is associated with one ormore hop records describing affiliates that referred the customer toproducts of vendors and is associated with one or more order recordsdescribing purchase transactions of the customer with the marketplaceserver using a client device associated with the device record.
 17. Thecomputer system of claim 15, wherein the instructions when executed bythe computer processor are configured to perform further stepscomprising: receiving, from the first client device of the customer, arequest to purchase the product of the vendor; identifying data recordsassociated with the first client device of the customer; anddetermining, from the data records associated with the first clientdevice, whether an affiliate referred the product to the customer; anddetermining, from the data records that an affiliate did not refer theproduct to the customer.
 18. The computer system of claim 15, whereindetermining the affiliate that referred the product comprises:determining a first affiliate and a second affiliate that referred theproduct to the customer; and compensating the first affiliate and thesecond affiliate for referring the product to the customer.
 19. Thecomputer system of claim 18, wherein the compensation distributed to thesecond affiliate is less than the compensation distributed to the firstaffiliate.
 20. The computer system of claim 18, wherein the compensationdistributed to the second affiliate is greater than the compensationdistributed to the first affiliate.